System and method of transmitting data messages between subscriber units communicating with/between Complementary/Disparate Networks

ABSTRACT

A system and method for enabling a first device ( 502, 504, 506 ) that may optionally roam between at least first and second wireless networks ( 500, 1102 ) to communicate with a second device ( 502, 504, 506 ) that may optionally roam between the at least first and second wireless networks ( 500, 1102 ). The devices ( 502, 504, 506 ) are preferably registered to each network in which the device may roam. A routing switch ( 1112 ) first transmits a data message to the receiving device at the last known location of the receiving device. If a negative acknowledgement is received, the message is routed to all other networks to which the receiving device is registered, either serially or in parallel, depending upon the configuration of the transmitting network. Routing devices ( 1112 ) and/or gateways ( 1110 ) are preferably provided for each network ( 500, 1102 ) to provide any required protocol and/or message format conversions.

RELATED APPLICATIONS

[0001] This application claims priority from U.S. provisionalapplication serial No. 60/173,742 filed on Dec. 30, 1999 and entitled“(1) ACE Advantages, (2) ACE Redundancy, (3) ACE Manager ProblemDiagnosis Tool, (4) Bell Mobility (Canada) Connectivity, (5) Fixed PointPolling Service”, the details of which are hereby incorporated byreference.

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates generally to a system and method ofenabling a first wireless subscriber unit (SU) (e.g., a wirelesscommunication SU) communicating with or registered to at least a firstnetwork to transmit/receive data to/from a second SU communicating withor registered to at least a second network. The present invention alsogenerally relates to the exchange of data between wireless communicationsystems and/or complementary networks, and the exchange of data betweenSUs communicable with such wireless communication systems. Moreparticularly, the present invention relates to a system and method ofenabling such transmission in a manner that is transparent to the SUs.

[0004] 2. Background Description

[0005] FIGS. 1-3 show a prior art radio frequency (RF) transmissionsystem 100, as disclosed in U.S. Pat. No. 5,819,172, incorporated hereinby reference, for transmitting information from one of a plurality oforiginating processors A-N to at least one of a plurality of destinationprocessors (A-N ) which may be transported during operation. The system100 includes at least one gateway switch 150 that stores informationreceived from one of the at least one originating processor prior totransmission of the information to the at least one destinationprocessor; a RF information transmission network 130 for transmittingstored information received from one of the at least one gateway switch150 by RF transmission to at least one destination processor; and atleast one interface switch 162 that connects a gateway switch 150 to theRF transmission network 100 and transmits stored information receivedfrom one of the at least one gateway switch 150 to the RF informationtransmission network 100.

[0006] The information is transmitted to a receiving interface switch bythe electronic mail system in response to an address of the receivinginterface switch which has been added to the information originated bythe originating processor by either the originating processor or gatewayswitch 14. The information is transmitted from the receiving interfaceswitch to the RF information transmission network 130 with an address ofthe destination processor to receive the information which has beenadded by either the originating processor, a gateway switch or thereceiving interface switch.

[0007] More particularly, FIG. 2 illustrates a block diagram of theconnection between a plurality of gateway switches with mailboxes 150 indifferent electronic mail systems to the RF information transmissionnetwork 160. Multiple gateway switches with mailboxes 150 from a singleelectronic mail system 1-N may be connected to each interface switch 162instead of the connection of a single gateway switch with a mailbox to asingle interface switch as illustrated. A plurality of interfaceswitches 162 connect information transmitted from at least oneelectronic mail system as illustrated in FIG. 1. Optionally, a pluralityof electronic mail systems 1-N are connected to a data input port, ofthe RF information transmission system which is preferably hub switch116. The dotted line communication paths 163 illustrate optionalinformation transmissions in which information from a plurality ofdifferent electronic mail systems is concentrated at a single interfaceswitch 304. The dotted line communication paths 161 illustrateconnections to additional gateway switches with mailboxes 150 withinelectronic mail systems 1-N.

[0008] The interface switches,162 function as a security check todetermine that information transmissions originating from a gatewayswitch with mailbox 150 represent transmissions which should be coupledto a hub switch 116 of the RF information transmission network 160. Thesecurity check is performed by the interface switch 162 comparing theidentification number of the RF receiver 119 which has been added byeither an originating processor A-N or a gateway switch with mailboxes150 with permissible identification numbers or the interface switchperforming the addition of the identification number.

[0009] The interface switch 162 also removes information added by theelectronic mail system 1-N to the information originated by theoriginating processor A-N from the stored information received from oneof the gateway switches 14, and adds information used by the RFinformation transmission network 130 during transmission of theinformation originated at the originating processor to a RF receiver 119in the RF information transmission network 130 which receives theinformation and transfers it to the destination processor A-N.Additionally, the interface switch 162 encodes data, which is requiredto format the display of the cathode ray tube (CRT) of the destinationprocessor for the electronic mail system to which the destinationprocessor is connected, in the form of a character or characters whichare decoded by either the RF receiver 119 or the destination processorA-N. This information is added in decoded form back to the informationwhich is processed by the destination processor with a format of theelectronic mail system to which the destination processor A-N isconnected.

[0010] The interface switches 162 also function to store informationwhich has been stored by at least one gateway switch 150 that isreceived from a plurality of originating processors, and assemble theinformation from a plurality of originating processors into a packethaving a predetermined format and transmit the packet to the hub switch116 within the RF information transmission network 160. The hub switchis the preferable node in the RF information transmission network towhich communications from the gateway switches 150 should be transmittedas a consequence of it having jurisdiction over both local access andtransport area (LATA) switches 150 and the local switches 112 in the RFinformation transmission network, which results in lesser networkoverhead.

[0011] The hub switch 116 receives the packet from the receivinginterface switch 162 and disassembles the packet into information fromthe plurality of originating processors. The originating processors areeither within a single electronic mail system such as system 1, or froma plurality of electronic mail systems, such as systems 1-N, or fromoutside of any electronic mail system from at least one additionalprocessor 312 which is connected directly to interface switch 162 tooriginate information to be transmitted to a destination processor A-Nin an electronic mail system as described below. The RF informationtransmission network 130 transmits the disassembled information from thehub switch 116, including the identification number of the RF receiver119 transferring information, to the destination processor A-N to alocal switch 112 storing the file identified by the identificationnumber and any destination of the RF receiver in the RF informationtransmission network to which the information and identification numberis to be transmitted by the RF information transmission network, andadds any destination of the RF receiver to the information. The RFinformation transmission network, in response to any added destination,transmits the information and identification number to the destinationfor RF broadcast to the RF receiver 119 for transfer to the destinationprocessor A-N.

[0012] The information is transmitted to a receiving interface switch162 from one or more gateway switches 150 by one or more electronic mailsystems 1-N in response to an address of the receiving interface switchwhich has been added to the information originated by the originatingprocessor by either the originating processor or gateway switch. Theinformation is transmitted from the receiving interface switch 162 tothe RF information transmission network with an address of thedestination processor, such as a name of a user of the destinationprocessor A-N, to receive the information which has been added by eitherthe originating processor A-N, a gateway switch 150 or the receivinginterface switch 304.

[0013] Preferably, the address of the receiving interface switch is acode word, such as “TF-MOBOX”, which is recognized throughout theelectronic mail system when appended to information as directing theinformation to be transmitted to the interface switch 304. The addressof the destination processor is preferably the identification number ofthe RF receiver 119 within the RF information transmission network 160.The address of the receiving interface switch may be added to theinformation originated by the originating processor, by a gateway switch150 or by the originating processor A-N. The address of the receivinginterface switch 162 may be added to the information by matching anidentification of the destination processor A-N which may be the name ofthe individual utilizing the processor or some other information to addan address of an interface switch such as the aforementioned “TF-MOBOX”stored with the matched identification of the destination processor tothe information as the address of the receiving interface switch.

[0014] Alternatively, the originating processor may be used to add theaddress of the receiving interface switch 150 by inputting the addressof the receiving interface switch (TF-MOBOX) along with anidentification of the destination processor A-N (name of recipient usingthe processor). The originating processor A-N may also add the addressof the receiving interface switch 162 by matching an identification ofthe destination processor (name of the user of the processor) with astored identification of a destination processor and adding an addressof the interface switch (TF-MOBOX) stored with the matchedidentification of the destination processor to the information as theaddress of the receiving interface switch.

[0015] The identification number may be added to the informationoriginated by the originating processor or, alternatively, maybe addedby the originating processor by matching an identification of thedestination processor (the name of the user of the processor) with astored identification of a destination processor (the authorized user ofthe destination processor) and adding an identification number storedwith the matched identification of the destination processor to theinformation as the identification number of the RF receiver 119.Alternatively, the aforementioned matching process may be performed byeither the gateway switch 150 or the interface switch 304. Theadditional processors 312 originates information from outside of anyelectronic mail system. The processors 312 provide an address of atleast one destination processor in an electronic mail system, such asthe name of the user, to receive information transmitted by the RFinformation transmission system 160, or an identification number of theRF receiver 119 receiving information and transferring the informationto the destination processor. The interface switch 162 which receivesthe information from each processor 312 adds information used by the RFinformation transmission network 130 during transmission of theinformation to the RF receiver 119 receiving the information in the samemanner as described above with respect to the interface switch 304.

[0016] Processors 312 are connected directly to the interface switch 162and are only required to have a telephone modem and support programmingto format information for RF transmission to a destination processor A-Nwithin any one of one or more electronic mail systems 1-N. Theprocessors 312 are not required to have the necessary electronic mailsystem software present in originating processors A-N orinterconnections with an electronic mail system. As a result of theconnection to the interface switch 304, information originating from theadditional processors 312 may be transmitted by RF transmission to adestination processor A-N within any one or a plurality of electronicmail systems with the user of the processor 312, the processor 312 orthe interface switch 162 only having to supply an identification numberof the receiver 119 to input information into the RF informationtransmission system 130 for RF transmission to a destination processor.

[0017] The difference between originating information by one of theadditional processors 312 outside of any electronic mail system andoriginating information by one of the processors within one of theelectronic mail systems is that the direct connection of the additionalprocessor to the interface switch 162 eliminates the requirement for theadding of an address of the interface switch 162 which is required bythe electronic mail systems to forward the information to the interfaceswitch where necessary formatting of the information to be compatiblewith the RF information transmission system is performed. The interfaceswitch 162 packetizes information originating from the additionalprocessors 312 in the same manner as described above with respect toinformation originating from within an electronic mail system.

[0018] Information from within an electronic mail system and originatingfrom additional processors 312 outside of the electronic mail system maybe formatted into the same packets which are forwarded to the hub switch116. Additionally, interface switch 162 may be connected only to theadditional processors 312 to provide an interface only for processorsoutside of any electronic mail system to destination processors A-Nwithin one or more electronic mail systems 1-N. The only informationwhich is necessary to be inputted by the additional processors 312 isthe address of the destination processor (user of the processor). Theaddition of the identification number of the receiver 119 may be addedby matching of an identification of the destination processor withstored destination processors within the additional processor 312, orthe interface switch 162 with an identification number of the receiver119 stored with an identification of a destination processor A-N used asan identification of the destination processor upon a match having beenmade.

[0019] Prior art FIGS. 1-3, however, do not generally relate to, forexample, a system and method of enabling a first wireless SU registeredto or communicating with a first network to transmit/receive datato/from a second SU registered to or communicating with a secondnetwork.

[0020] Packet or data communication between data networks is not fullystandardized. As a result, a number of different standards, protocols,etc. are available to provide packet or data communication between, forexample, a first SU registered to or communicating with a first networkto transmit/receive data to/from a second SU registered to orcommunicating with a second network. Such differences in standards areespecially true with respect to maintaining the location andregistration status of a particular SU. The manner in which such data ismaintained is referred to as “mobility management” and is needed forenabling a SU to freely travel or roam within a particular network.

[0021] U.S. Pat. No. 6,137,791 to Frid et al. discloses a specializedroaming mechanism enabling a mobile station to transmit data from afirst network utilizing a Mobile internet protocol (IP) Method (MIM) andto a second network utilizing a Personal Digital Cellular MobilityMethod (PMM). As shown in prior art FIG. 4, which shows a mobile station490 associated with an MIM network 400 within a PMM network 10. The MIMmobile station 490 is associated with a home agent (HA) 320. Such a HAcan be located within the MIM network 400 or within an external datanetwork.

[0022] In order to transmit towards the mobile station, the HA 440 needsa corresponding foreign agent (FA) located within the visited geographicarea. However, since conventional PMM network 410 does not include a FA,no IP tunnel can be established between the HA 440 and the PMM network10. An IP tunnel carries a foreign protocol within a TCP/IP packet(e.g., IPX (Internetwork Packet Exchange) can be encapsulated andtransmitted via TCP/IP). Therefore, a FA 420 is introduced into the PMMnetwork 410 to effectuate an IP tunnel between the HA 440 and the PMMnetwork 10.

[0023] When the MIM mobile station 490 is in a new geographic areawithin the PMM network 10, the mobile station 490 performs aregistration in a conventional manner by transmitting a locationregistration request over the air-interface 402. The mobile station 490may further be associated with a data terminal equipment (DTE) 20A. Thebase station (BS) 444 receives the request and forwards it to theconnected visited mobile switching center (VMSC) 40. The VMSC 40, inturn, performs an authentication procedure by transmitting a SubscriberAuthentication Information Retrieval Request 411 to an associatedgateway location register (GLR, also known as a visitor locationregister VLR) 620. The GLR 620, in turn, transmits an Internet-workingAuthentication Information Retrieval Request signal 415 to a homelocation register (HLR) 455 associated with the registering mobilestation 20. The associated HLR 455 authenticates the subscriber andinforms the GLR 430 with necessary authentication data via Inter-workingAuthentication Information Retrieval Response signal 660. Such datainclude the authentication keys associated with the mobile station 20.

[0024] The GLR 620, in turn, informs the results 413 back to therequesting VMSC 40. The VMSC 442 then transmits an AuthenticationRequest signal to confirm the authentication data with the mobilestation 20. In response, the mobile station 490 provides the requestedauthentication data via an authentication response signal 690. Afterverifying the received data and confirming the mobile station 20, alocation registration acknowledgment signal is transmitted to the mobilestation 490 by way of air-interface 402. The mobile station 490 is nowregistered to access the serving mobile telecommunications network fornormal mobile services (i.e., voice call connection).

[0025] After establishing the authentication procedure, the associatedDTE 490A enters packet mode and instructs the mobile station 490 totransmit a packet communication registration request signal to thevisited packet mobile switching center (VPMSC) 480 through the VMSC 40.Such a separate request is necessary to further enable the mobilestation 490 to communicate instead of normal voice data. The VPMSC 480may further communicate with the associated GLR 430 to authenticate themobile station 490 for packet data communication (not shown). In return,the VPMSC 480 may also transmit a packet authentication request signal720 to the mobile station 20. The mobile station 490 may then respondwith a packet authentication response signal 730. After verifying thatthe mobile station 490 is authenticated to utilize packet communication,a packet communication registration response signal 740 is provided backto the mobile station 20. The mobile station 490 then enters packetmode.

[0026] For mobile stations belonging to the MIM network 400 andcurrently traveling within the PMM network 10, the VPMSC 480 establishesan IP tunnel 455 with the newly created FA 310. More specifically, theVPMSC 480 creates a first IP tunnel 455 with a gateway packet mobileswitching center (GPMSC) 450 serving the PMM network 10. The GPMSC 70,in turn, interfaces with the FA 310. As described above, since themobile station 490 is associated with the MIM network 300, a HA 440associated with mobile station 490 receives all incoming packet dataaddressed towards the mobile station 490 currently roaming within thePMM network. Since the HA 440 requires a FA to establish an IP tunneland to communicate received packet data therebetween, the new FA 420 asdescribed above is introduced within the PMM network 410 in accordancewith the teachings of the present invention.

[0027] The DTE 490A connected to the mobile station 490 then performs aPPP establishment procedure towards the FA/GPMSC 310/70. The DTE thensends a Mobile IP Agent Solicitation message to effectuate an IPconnection with the home network. The new FA node 420 of the PMM network410 responds with a mobile IP agent advertisement message. The DTE thensends a mobile IP registration request message to the FA 310. The FA 420then identifies the HA 440 associated with the roaming mobile station490 and forwards the message to the identified HA 320. The HA sends amobile IP registration reply message 810 back to the FA/GPMSC 310/70 andfurther establishes a second IP tunnel 408 with the serving FA 310. TheFA/GPMSC 310/70 then forwards such a message 820 to the DTE 20A.

[0028] A data delivery between the HA 440 and the DTE 490A iseffectuated thereafter. For example, for incoming data packets 406addressed towards the DTE 20A, the packets are initially received by theHA 440 and routed to the DTE 490A via the second IP tunnel 408 and thefirst IP tunnel 750. For outgoing data packets 404 originated from theDTE 20A, the packets are first routed by the first IP tunnel 455 towardsthe FA 420 and then, for example, to an appropriate external network900.

[0029] The GPMSC 450 associated with the PMM network 410 furtherincludes an interface module 460 for interfacing and communicating withthe newly introduced FA 310. Furthermore, in order to facilitate theDTE's PPP establishment request, the GPMSC 450 is further equipped witha PPP server 610.

[0030] However, unlike the present invention which is directed to datacommunication between two or more disparate networks, U.S. Pat. No.6,137,791 is directed to voice communication between a first data packetnetwork using a MIM and a second data packet network utilizing aPersonal Digital Cellular Mobility Method (PMM) . There is currently noknown general mechanism for enabling SUs to transmit and/or receiverelectronic messages while communicating with or utilizing a disparate,different, and/or incompatible second packet network.

[0031] Accordingly, there is a need for a system and method to enable,for example, a SU that transmits data to efficiently and/or seamlessly(e.g., transparent to the SUs) communicate from a first mobiletelecommunications network to, a destination at a second mobiletelecommunications network.

SUMMARY OF THE INVENTION

[0032] It is a feature and advantage of the present invention to enabletwo or more SUs to efficiently and/or seamlessly transmit data betweentwo or more different, disparate and/or communicably different networks.

[0033] It is another feature and advantage of the present invention toenable SUs to communicate between two or more different, disparateand/or communicable different networks without requiring the SUs to bemodified and/or communicate in a specialized manner.

[0034] It is still another feature and advantage of the presentinvention to enable data to be transmitted from a SU in a first networkto a SU in a second network by physically and/or logically modifyingonly the first network and/or the second network.

[0035] It is still another feature and advantage of the presentinvention to enable data to be transmitted from a SU in a first networkto a SU in a second network without having to modify the hardware andoptionally the software of the SU in the first network and/or the SU inthe second network.

[0036] In one embodiment, the present invention provides a system andmethod for enabling SUs to seamlessly transmit data to any number ofcomplementary networks. That is, both the sending and receiving SUs areunaware of the fact that they are sending data to, receiving data from,a SU in a different network. The primary network is preferably aterrestrial network, whereas the secondary network(s) can be either asatellite network (e.g., NORCOM) and/or a terrestrial network (e.g.,Bell Mobility Canada). Other networks may alternatively be used. Thus,with the present invention, SUs can communicate with and optionally beregistered with, for example, at least two different networks, andtransmit data therebetween, where the networks may optionally be usingdifferent data communication protocols.

[0037] One embodiment of the present invention enables the primarynetwork to look like a host to one or more complementary networks whensending a message thereto. In this embodiment, the SUs communicateand/or register either with each of the primary and/or one or moresecondary networks. For example, if the primary network is a U.S. basednetwork, and a SU normally residing in the U.S. travels to, for example,Canada, the SU can send an e-mail using the secondary network, whichtransmits the e-mail message to the designated SU in the primary and/orsecondary network.

[0038] The present invention provides, for example, an interface orinput to the one or more complementary networks by, for example,establishing a TCP/IP connection, and appropriately formatting thetransmission headers. The primary network interfaces to each of the oneor more secondary networks, preferably as if it were a standard customerhost to the secondary network. This host connection can be facilitatedby a server or computer system that creates appropriate messagetransmission headers in accordance with the protocol used by thesecondary network. This enables the secondary network to interpret theheaders, and subsequently route the message to the designated SU. Aqueue manager within at least the primary network can be provided thatkeeps track of where the SUs are located (e.g., in the primary networkor a complementary network), and thus where messages need to be sent toreach each respective SU in either the primary or secondary network.

[0039] In the case of an e-mail message sent from a SU in the primarynetwork to a SU in a complementary network, the host computer may be,for example, a server associated with the e-mail or communicationservice of the primary network. If a SU in the primary network sends ane-mail message or data message to a SU in the secondary network, thesecondary network will recognize that the receiving SU is registeredthereto, and attempt to route the message to the designated SU.

[0040] In another embodiment, SUs in the complementary network can alsosend data messages to the primary network. The complementary network mayhave, for example, a gateway (or similar hardware and/or software) thatenables the complementary network to send messages to the primarynetwork. In this embodiment, physical and/or logical changes may berequired to the secondary network. However, advantageously no suchchanges are required to be made to the secondary network when thesecondary network only receives messages (i.e., does not transmitmessages to another network).

[0041] The present invention contemplates that the transmitted data isfirst sent to the last known network that the intended receiving SU waslocated. If a connection cannot be established with the SU in thatnetwork, the data will then be sent to the other (or one of the other)network(s) to which the SU is registered. In the case of multiplecomplementary networks or in alternative embodiments of the invention,the data can be sent serially, to one complementary network at a time,or in parallel (i.e., substantially simultaneously to all networks towhich the SU is registered).

[0042] There has thus been outlined, rather broadly, the more importantfeatures of the invention in order that the detailed description thereofthat follows may be better understood, and in order that the presentcontribution to the art may be better appreciated. There are, of course,additional features of the invention that will be described hereinafterand which will form the subject matter of the claims appended hereto.

[0043] In this respect, before explaining at least one embodiment of theinvention in detail, it is to be understood that the invention is notlimited in its application to the details of construction and to thearrangements of the components set forth in the following description orillustrated in the drawings. The invention is capable of otherembodiments and of being practiced and carried out in various ways.Also, it is to be understood that the phraseology and terminologyemployed herein are for the purpose of description and should not beregarded as limiting.

[0044] As such, those skilled in the art will appreciate that theconception, upon which this disclosure is based, may readily be utilizedas a basis for the designing of other systems and methods for carryingout the several purposes of the present invention. It is important,therefore, that the claims be regarded as including such equivalentconstructions insofar as they do not depart from the spirit and scope ofthe present invention.

[0045] Further, the purpose of the foregoing abstract is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The abstract is neitherintended to define the invention of the application, which is measuredby the claims, nor is it intended to be limiting as to the scope of theinvention in any way.

[0046] These together with other objects of the invention, along withthe various features of novelty which characterize the invention, arepointed out with particularity in the claims annexed to and forming apart of this disclosure. For a better understanding of the invention,its operating advantages and the specific objects attained by its uses,reference should be had to the accompanying drawings and descriptivematter in which there is illustrated preferred embodiments of theinvention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The Detailed Description including the description of a preferredstructure and method as embodying features of the invention will be bestunderstood when read in reference to the accompanying figures wherein:

[0048]FIG. 1 illustrates a prior art block diagram of a known messagingsystem;

[0049]FIG. 2 illustrates a prior art block diagram of the connection ofa plurality of electronic mail systems through a plurality of interfaceswitches to an input port of an RF information transmission network;

[0050]FIG. 3 illustrates a prior art block diagram of the transmissionof information originating from a plurality of electronic mail systemsto a plurality of destination processors;

[0051]FIG. 4 is a prior art block diagram of two different packet datanetworks illustrating the roaming of a mobile station transmitting voicedata from a first packet data network to a second packet data network;

[0052]FIG. 5 is a schematically simplified representation of theMotient^(SM) terrestrial communications network;

[0053]FIG. 6 shows a data flow of a message sent inbound from a hostcomputer to a SU.

[0054]FIGS. 7a and 7 b, taken together, show a data flow of a messagefrom a host computer to a SU using the MDC-4800 protocol;

[0055]FIGS. 8a and 8 b, taken together, show a data flow of a messagefrom a SU to a host computer using the MDC-4800 protocol;

[0056]FIG. 9 shows a data flow of a message from a host computer to a SUwhen the SU is not available;

[0057]FIG. 10 shows a data flow of a message from a SU to a hostcomputer when the host computer is disconnected;

[0058]FIG. 11 is a schematically simplified representation of theoverall complementary network system;

[0059]FIG. 12 is a representative simplified block diagram of a primaryand a secondary network, which also illustrates an overview of themethod according to the present invention;

[0060]FIG. 13 is a more detailed block diagram of FIG. 12;

[0061]FIG. 14 is an overview of the inputs to and outputs from theReverse SCR server according to the present invention;

[0062]FIG. 15a shows an example of a first data format that may betransmitted from the primary network to the complementary network;

[0063]FIG. 15b shows an example of a second data format that may betransmitted from the primary network to the secondary network; and

[0064]FIGS. 16a and 16 b, taken together, is a flowchart of the processfor transmitting data to a SU that can travel between two or morenetworks in accordance with the present invention.

DETAILED DESCRIPTION

[0065] Reference now will be made in detail to the presently preferredembodiments of the invention. Such embodiments are provided by way ofexplanation of the invention, which is not intended to be limitedthereto. In fact, those of ordinary skill in the art may appreciate uponreading the present specification and viewing the present drawings thatvarious modifications and variations can be made.

[0066] For example, features illustrated or described as part of oneembodiment can be used on other embodiments to yield a still furtherembodiment. Additionally, certain features may be interchanged withsimilar devices or features not mentioned yet which perform the same orsimilar functions. It is therefore intended that such modifications andvariations are included within the totality of the present invention.

[0067] In accordance with the present invention, it is preferred thatfor terrestrial transmission a network such as the Motient^(SM) network(previously known as the ARDIS^(SM) network) shown in FIG. 5 beutilized. Terrestrial networks of this nature provide secure, portable,two-way communication between, for example, wireless data terminalsand/or mobile data terminals.

[0068] The Motient^(SM) network 500 is a terrestrial wireless two-waydata network that is based on Motorola's RD-LAP technology. It wasoriginally developed and jointly owned by Motorola and IBM. In 1995Motorola acquired 100 percent ownership of what was then called theARDIS® (Advanced Radio Data Information Services) network. In 1998,ARDIS® was acquired by American Mobile Satellite Corporation (nowMotient Corporation).

[0069] The Motient^(SM) network 500 covers at least ninety percent ofthe urban business population and more than 400 metropolitan area in theUnited States, Puerto Rico and the Virgin Islands. Two standardair-interface protocols have been developed for the network 500. Thestandard MDC-4800 protocol provides a 4800 bit/sec service, and thestandard RD-LAP protocol provides a 19.2 kbit/sec service.

[0070] The network 500 allows SUs such as an intelligent terminal orcomputing device 502, handheld device 504, and/or other communicationsdevice 506 to transmit and/or receive data messages. SUs 502, 504, 506therefore, typically have a radio frequency (RF) modem for sending andreceiving signals. The RF modem utilizes the MDC-4800 and/or RD-LAPprotocols to enable to SUs to gain access to the Motient^(SM) network500. In the event the a network other than the Motient^(SM) network 500is utilized, other air-interface communication protocols may be used.For example, if a MOBITEX network is used, the air-interface protocolwould be Gaussian minimum shift keying (GMSK).

[0071] The network 500 has over 1750 base stations (510) that provideservice throughout the United States, Puerto Rico, and U.S. VirginIslands. Each base station 510 covers a radius of approximately 15-20miles. The base stations 510 are radio frequency towers that transmit orreceive radio signals between SUs 502, 504, 506 and the RadioFrequency/Network Control Processors (RF/NCPs) 512. Base stations 510transmit and receive radio signals, preferably using a narrow band FMtransmitter and receiver operating in the 800 MHz frequency band. Thereare separate frequencies for the transmit path and the receive path;together these two frequencies represent a full duplex channel thatnormally transmits data at 4800 bps in both directions. Other standardtransmission methods may alternatively be used in other standardcommunication systems.

[0072] In operation, for a message “inbound” to the network 500 from aSU 502, 504, 506, the signal is “heard” or received by the base stations510 and sent over dedicated leased lines 516 to a RF/NCP 512. Thenetwork 500 employs an automated roaming capability that allows the freemovement of SUs 502, 504, 506 between cities and between multiplechannels within a given city. This capability allows the SUs 502, 504,506 to freely move (roam) across the country and take advantage of allthe network services that are available in every locale.

[0073] The RF/NCPs 512 are high-speed computers that interconnectmultiple base stations 510 with the standard ARDIS® Connect Engine(s)(ACEs) 514. A number of RF/NCPs 512 are located together serving aparticular geographical area, each being connected by high speed digitalphone service to one of the ACEs 514, which route messages to adestination such as a customer host computer 508 that is directlyconnected to the network 500 by, for example, a leased telephone line ora value added network.

[0074] RF/NCPs 512 manage the RF resources, including the base stations510 and data sent over the radio channels. Both inbound and outboundchannels are managed using different delivery strategies. The RF/NCPs512 evaluate the strength of e signal received from every wirelessdevice transmission at each base station for each detected inbound datapacket. Alternatively, the wireless device or the system may evaluatesignal strength and report back to the RF/NCP 512. The RF/NCP thenselects the best base station 510 to communicate with that particularwireless device and will send the next outbound message through thatbase station.

[0075] The RF/NCPs 512 also help manage the roaming capability of thenetwork 500. SUs 502, 504, 506 can automatically move (roam) between anyof the network 500 frequencies on either of the two protocols (MDC-4800and RD-LAP 19.2), or between any of the configured network 500 layersthat have been configured for in-building or on-street usage. Throughperiodic transmission of “channel market messages,” each SU 502, 504 506is provided with the most efficient service available in that area. EachRF/NCP 512 also passes information, via a high speed digital line,relating to source, destination and length of each message to an ACE 514that enables the network 100 to do network analysis of traffic densityat each base station 510.

[0076] An ACE 514, in turn, passes information back to a RF/NCP 512concerning whether the SU 502, 504, 506 is properly registered to thenetwork 500 and, if so, what level of service is provided to therespective subscriber 502, 504, 506. The ACEs 514 are general purposecomputers that act as the heart of the network 500. The ACEs 514 routemessages to the proper destination, store subscriber registrationinformation including entitlement, and perform accounting and billingfunctions. The ACEs 514 also serve as a point of connectivity to, forexample, host 508, perform protocol conversion, and perform network 500troubleshooting and test functions. A plurality of ACEs 514 areinterconnected through dedicated lines, with alternate paths availablefrom each switch as a contingency measure against line interruptions.The linking between host 508 and an ACE 514 is generally accomplishedusing asynchronous, bisynchronous, Systems Network Architecture (SNA),or X.25 dedicated circuits.

[0077] The wireline network 516 provides communication between thecustomer host computer 508, the ACEs 514, the RP/NCPs 512, and the basestations 510. The wireline network 516 is equipped with communicationsequipment that relays customer messages. This equipment includesintelligent multiplexers, leased telephone circuits, high-speed modemsor digital service units, and modems for both RF/NCP 512 and host 508connectivity. Accordingly, the various functionality performed by ACE514 and the other one or more RF/NCPs 512, and base stations S10 mayoptionally be distributed in various parts/manners to those networkcomponents in accordance with alternative embodiments of the invention.

[0078] Inside every cell, the SUs 502, 504, 506 access the network 500using, for example, a random access method called data sense multipleaccess (DSMA). Before every transmission, a SU 502, 504, 506 listens toa base station 510 to determine if the base station is busy. The SUs areallowed to transmit only when a base station 510 is not busy and/or havecapacity to provide service.

[0079] Referring now to FIGS. 6-9, typical data flows are shown for thenetwork 500, and are described in detail in ARDIS DataTAC 4000 SoftwareDevelopers Reference Guide, Revision 2.0, Jan. 1997, incorporated hereinby reference. In these figures, a number in parenthesis (e.g., (1), (5),etc.) refers to that portion of the flow of a message in accordance withthe present invention. FIG. 6 shows a message sent inbound from a hostcomputer 508 to a SU 502, 504, 506. The host computer 508 performscompression and/or encryption on data, and is connected to the ACE 514,preferably by an application program interface (API) or standard gatewayconnection. As will be discussed in further detail herein, the hostcomputer 508 sends an FIBS message header to the ACE 514, whichindicates to the ACE 514 that there is an incoming message.

[0080] The ACE 514 receives the logical “IB” message from host computer508, validates the customer to device, determines the RF/RNC 512 thatthe message should be sent to, and checks if the transmitting SUrequires an acknowledgement message (ACK) message. The RF/RNC 512,preferably by a lookup table, sends message packets to the “best” basestation 516 (e.g., base station 516 having the strongest signalreception with respect to the RF/RNC 512), controls base station 516transmission, and optionally sends an ACK message to ACE 514 toindicate, for example, a successful transmission. Similarly, the RF/RNC512 may also transmit a negative acknowledgement (NAK) message thatindicates that the SU 502, 504, 506 may be out of range or out ofservice. The base station 516 then transmits message packets from theRF/RNC 512 and optionally waits for an ACK message.

[0081]FIGS. 7a and 7 b, taken together, show a representative messageflow from a message sent from a host computer 508 to a SU 502, 504, 506using the MDC-4800 protocol. With regard to FIG. 7a, a message is sentfrom the customer host 508 to the ACE 514 (601). The message can beoptionally and preferably segmented into packets (e.g., “A,” “B,” “C”,etc.) (602). The first packet is delivered to the RF/RNC 512 where thedestination modem was registered when it was last active. The RF/RNC 512delivers the first packet (e.g., packet A) to base station 516 z(optimal base station for delivery) (603). The base station 516 ztransmits the packet to a wireless modem (604), which responsivelytransmits an ACK packet to the base station 516z and then back to theRF/RNC 512 and ACE 514 (605, 606, 607).

[0082] Referring now to FIG. 7b, the rest of the packets (e.g., packetsB, C, etc.) comprising the message are sent in sequence to the wirelessmodem and are acknowledged respectively (608, 609). The modem assemblesthe logical message and delivers it to the application (610). A messageacknowledgement is delivered from the ACE 514 to the customer's server508 (if requested by the server) (611).

[0083]FIGS. 8a and 8 b, taken together, show a representative messageflow from a SU 502, 504, 506 to customer host 508. A message is sentfrom the SU 502, 504, 506 application to a wireless modem (801). Themessage is segmented into packets (e.g., “A,” “B,” “C,”, etc.) (802).The first packet (A) is transmitted to base stations in the area (e.g.,512 x and 512 y). If the RF/RNC 516 receives multiple copies of themessage, it eliminates duplicates. The RF/RNC 516 delivers the firstpacket (A) to the ACE 514 (804). Base station 512 y is chosen, forexample, based on predetermined and/or standard criteria, as the mostappropriate delivery route. An acknowledgment packet is delivered fromthe RF/RNC 516 to base station 512 y (805). The acknowledgement packetis then delivered to the wireless modem via RF (806). Referring now toFIG. 8b, the process is repeated for the additional packets comprisingthe logical message (807, 808). The message is assembled, for example,at the ACE 514 (809), and subsequently sent to the application (810).The ACE 512 returns an acknowledgment to the wireless modem (811).

[0084]FIG. 9 shows a representative message flow from customer host 508to a SU 502, 504, 506 when the SU is not available. A message is sentform the customer host 508 to the ACE 514 (901). The data message can becopied into a packet and delivered to the RF/RNC 516 where thedestination modem was registered or located when it was last active(902). The RF/RNC 516 delivers the data message, for example, in packetformat to base station 512 z (where the last activity occurred) (903).The base station 512 z transmits the data message to the wireless modembut does not receive an acknowledgment back, and consequently triessending the message a second time (904). The base station that servicedthe client next to last time is optionally tried initially (e.g., 512 y)(905). The ACE 514 transmits a NAK packet to the customer host 508 toindicate that the message could not be delivered (if requested by theserver) (906).

[0085] Referring now to FIG. 10, a representative message flow from a SU502, 504, 506 to a customer host 508 is shown, where the customer hostis disconnected. A message is sent from the SU 502, 504, 506 applicationto the wireless modem (1001). The message is copied, for example, into astandard packet and transmitted to base stations in the area (e.g., 512x and 512 y) (1002). The RF/RNC 516 receives multiple copies of themessage and eliminates duplicates (1003). The RF/RNC 516 delivers thepacket to the ACE 514 (1004). An attempt is made to send the message tothe customer host 508, where line problems, for example, areexperienced. If the message cannot be delivered, ACE 514 discards themessage (1005). An error message is sent back to the wireless modemindicating that the customer host 508 is down (1006).

[0086] Referring now to FIG. 11, a high level architecture of the system1100 in accordance with the present invention is shown. ACE 514 allows aSU 502, 504, 506 to be registered to a plurality of networks orcomplementary networks (e.g., a primary terrestrial network 500, asecondary terrestrial network 1102, and/or a satellite network 1106).The primary network can be, for example, the Motient^(SM) network 500,the secondary network 1102 can be, for example, the Bell Mobilitynetwork, and the satellite network 1106 can be, for example, the NORCOMsatellite network. Other networks may alternatively, or in addition, beused. The secondary network(s) preferably has at least one host computer508 that is connected to a gateway 1110. The host may also be optionallyconnected to the modem 1116 and/or routing switch 1112. Switch 1112preferably has a functionality substantially similar to the ACE 514,which will be described herein. Modems 1114, 1116 can be utilized toconnect the primary network 500 and secondary network 1102 via, forexample, landline 1118.

[0087] Referring now to FIG. 12, a more detailed architecture of thesystem 1100 (and environments thereof) as contemplated by the presentinvention is shown. Details of the architecture of the presentinvention, the manner in which messages are processed, and how SUs 502,504, 506 transmit and receive messages between the primary network andone or more secondary networks 1102 are explained herein.

[0088] A SU 502, 504, 506 that roams between the primary network 500,the secondary network 1102, and/or a satellite network 1106 willpreferably be registered using standard procedures and/or real-time viastandard identification procedures with each respective network. Itshould be further understood that the connection of the ACE 514 toswitch 1112 is perceived by the secondary network 1102 as it would anyother supported connection (e.g., X25). That is, in accordance with oneembodiment of the present invention, it is preferred that the ACE 514appear as a host to a switch 1112 (or equivalent thereof) of acomplementary network (e.g., 1102 and or 1106).

[0089] In operation, it is preferred that a message is sent from a SU502, 504, 506 and received by host computer 508 via any of the network500 supported line protocols (e.g., X.25). The line handler 1202 passesthe message to an appropriate protocol converter which, in this example,is a binary Standard Context Routing (SCR) 1204 converter. Binary SCRcan be used in host based routing when a SU 502, 504, 506 sends messagesto and/or receives messages from a host computer 508 connected to thenetwork 500. Host based routing is generally used for applications whichrequire a central repository of information or on-line service. Thistype of routing assumes that the host computer 508 server is in a fixedlocation and that the host computer 508 application(s) compliments theclient application—usually by providing more complex processing. It ispreferred that the host computer 508 is connected to the ACE 514 throughone of a variety of supported protocols (for example SNA LU6.2 or X.25).The physical connection to the ACE 514 can be, for example, a leasedline.

[0090] When a message is received from a SU 502, 504, 506 andsubsequently transmitted from the host computer 508 to a receiving SU502, 504, 506, SCR can be used for routing that message through thenetwork 500. SCR is an application header which flows between customerhost 508 and the network 500. This header is preferably placed at thebeginning of the user data. SCR provides for message control anddelivery acknowledgment, and can be used with the SNA LU 6.2 and X.25protocols. Other standard application headers may alternatively be usedthat performs or provides the functionality and/or data describedherein.

[0091] It is preferred that there are at least three types of SCRmessage headers: Basic Inbound (IB), Basic Acknowledgement (AB), andBasic outbound (BO). The IB header is preferably created in the customerhost 508 application software or communications software and flows fromthe customer host 508 to the network 500. The network 500 then directsthe message to the appropriate SU 502, 504, 506. The AB header iscreated by the network 500 and is sent to the customer host 508. An ABheader notifies the customer host 108 that the message sent to a SU 502,504, 506 was successfully delivered. The OB header is created by thenetwork 500 for messages sent to the customer host 508 from a SU 502,504, 506. Further information pertaining to the SCR protocol and theMotient^(SM) network can be found in the following documents: ARDISNetwork Connectivity Guide, June 1994; DataTAC Wireless Data Networks:Application Development Guide (Doc. No. 6804111L20-A), First Edition,November 1997; DataTAC Open Protocol Specifications Standard ContextRouting Release 1.0 (Doc. No. 68P04025C20-A), November 1995); ARDISDataTAC 4000 Software Developers Reference Guide, Revision 2.0, January1997. Each of the aforementioned documents are incorporated herein byreference in their entirety. Copies of these documents are submittedherewith. Other standard message headers may alternatively be usedproviding the functionality and/or data described herein.

[0092] At 1204, the SCR header is removed and an internal network 500control header is added. The message is forwarded to a request server1206, which reads the SU 502, 504, 506 profile, and the primary andsecondary network (e.g., network(s) 500 and/or 1102 and/or 1106)information is then added to the internal ACE 514 header.

[0093] The message is then routed to an assigned SU queue manager 1208,where the message is queued. If no other messages are queued, the SUqueue manager 1208 routes the message to the primary destination which,in this example, is the RNC Server 1210. The RNC server 1210 adds theappropriate radio frequency (RF) header for RF transmission, and routesthe message to the configured X.25 line handler 312 corresponding to theRNC associated with, for example, the current location of designated SU502, 504, 506. As shown in FIG. 5, the ACE 514 is actually a part of theMotient^(SM) network 500. Here, the ACE 514, via line handler 1212,transmits the message to, for example, a RF/NCP 512.

[0094] If, after a predetermined number of attempts the message cannotbe delivered, the network 500 returns, for example, a NAK 1214 messageto the X.25 line handler 1212. The line handler 1212 then routes(indicated by arrow 1216) the NAK 1214 back to the RNC server 1210,where the RF Header is removed.

[0095] The RNC Server 1210 then routes the message back to the SU queuemanager 1208, where the original message was queued. The SU queuemanager 1208 then routes the message 1220 to the available secondarydestination. This secondary destination could be, for example,complementary network 1102. In this case, the message is routed to thereverse SCR server 1222, which adds appropriate headers to the messageso that the network 500 looks like a customer host to the complementarynetwork 1102 and/or 1106.

[0096] Specifically, the reverse SCR server 1222 adds the appropriate IBSCR message header and forwards the message to the configured X.25 LineHandler 1224, which can send the message to, for example, switch 1112,which preferably views the connection as it would a standard hostconnection. Switch 1112 can then route the message to the network 1102as it would any other message to the designated SU 502, 504, 506. Asdiscussed with regard to FIG. 14, the response server 1220 isoperatively communicable with the reverse SCR server 1206. The responseserver 1220 manages any ACK and NAK messages between the network 500 andany complementary network(s) 1102.

[0097] A SU 502, 504, 506 in a complementary network 1102 and/or 1106can also transmit to a SU in the primary network 500. In this case, thecomplementary network 1102 and/or 1106, in effect, becomes functionallyequivalent to the primary network 500. As such, switch 1112 (orequivalent thereof) may need to be physically and/or logically modifiedto provide functionality similar to, or substantially similar to, theACE 514 That is, when the primary network 500 transmits to a secondarynetwork 1102 or 1106, no modification of the secondary network(s) 1102and/or 1106 are required since the primary network appears as any otherhost would to the secondary network(s). However, when the secondarynetwork 1102 and/or 1106 is transmitting to the primary network, andalso wants to provide the features of the present invention to itsassociated or registered SUs or customers, the secondary network may berequired to have a functionality similar to the ACE 514 to enable SU502, 504, 506 to transmit a message between the designated secondarynetwork (e.g., 1102) and one or more other networks (e.g., 500 and/or1106).

[0098] While the above description has focused one specific networkconfiguration, other network configurations are possible and may be usedwith the present invention to implement the functionality and featuresdescribed herein. For example, instead of using a host-based routingscheme as described above, the ACE 512 may also route from a first SU502, 504, 506 to a receiving Su 502, 504, 506 in the complementarynetwork 1102 and/or 1106, without using a host computer 1108, by using aconventional e-mail protocol such as the Post Office Protocol (e.g.,POP3, POP 4, etc.) or Simple Mail Transfer Protocol (SMTP). In thiscase, the Reverse SCR server 1222 can utilize, for example, the POP3and/or POP 4 and/or SMTP protocol, rather than the SCR.

[0099] In addition, a wireless transmission may be utilized between theprimary network 500 and the secondary network 1102. In this case, theReverse SCR Server 1222 can utilize, for example, the wireless MessageGenerator (MG) application user header, as described in theabove-referenced ARDIS DataTAC 4000 Software Developers Reference Guide,Revision 2.0, January 1997. Similarly, the Reverse SCR Server 1222 canconvert from a first RF protocol used by the primary network to a secondRF protocol used by the secondary network 1102 and/or 1106, and/orutilize the second RF protocol when transmitting to the secondarynetwork 1102 and/or 1106.

[0100]FIG. 13 shows a more detailed view of FIG. 12. Customer hostcomputer 508 may be, for example, a mainframe computer, mini computer,micro computer, and the like. It should be understood that a message canalso enter the ACE 514 from the network 500 via normal messagetransmission as discussed with regard to FIG. 5. The normal flow fromhost computer 508 to SU 502, 504, 506 occurs when a X.25 line handler1202, for example, detects an incoming message (1). Other line handlerscan also be provided (e.g., TCP/IP line handlers, LU 6.2 line handlers,and the like). Line handler information is preferably loaded as neededfrom database 1305. Similarly, network information is also preferablyloaded at startup 1304. The line handler 1202 generally determines whichprotocols) the customer host 508 uses to communicate with the ACE 514.For example, as previously discussed, the customer host 508 can talk tothe ACE 514 through either character SCR or binary SCR, which areprotocols that allows the host to, for example, specify thereceiving/destination SU.

[0101] Character SCR server 1302 reads the incoming message (2) andassociated SCR headers to determine what SU 502, 504, 506 the message isto be delivered to. Request server 1206 receives the message (3) andensures that the desired SU 502, 504, 506 exists (4). In one embodiment,such information can be stored, for example, in one or more databases.For example, the SU information database 1308 can store all valid SUidentification numbers (IDs). The customer information database 1310 canstore the type and level of service provided to each customer and/or SU,and/or data pertaining to usage fees and/or billing (6). The requestserver 1206 also ensures that the host computer 508 can communicate withthe intended SU 502, 504, 506.

[0102] The SU queue manager 1208 determines which network(s) (e.g.,network 500 and/or 1102 and/or 1106 shown in FIG. 11) the SU 502, 504,506 is registered to. In the case the SU 502, 504, 506 is identified asSU 123 (5), the SU registered to the network 500. The message istransmitted (7) to a RNC server 1210, which may, for example, placeappropriate transmission headers on the message. The message (8) is thensent to the network 500 via, for example, an X.25 line handler 1212 (or1212′). More than two line handlers may be provided. It is alsopreferred that when two or more line handlers are provided (e.g., linehandlers 1212 and 1212′), they receive/transmit messages on around-robin basis, so that there is substantially equal message trafficpassing over line handler 1212, 1212′. As shown, the line handlers 1212,1212′ are operatively connected to and communicable with the RNC subnetmanager 1210.

[0103] In the event the intended SU 502, 504, 506 is not available, theRF/RNC 512 will send a NAK (9) to the primary X.25 line handler 1212 andsubsequently to the RNC server 1210. In the event that the primary linehandler is down, the message can be sent via a secondary line handler1212′ (10). In the event the intended SU 502, 504, 506 is not available,the RF/RNC 512 can send a NAK (11) to the secondary X.25 line handler1212′ and subsequently to the SU queue manager (12).

[0104] The SU queue manager 1208 receives notification (12) that themessage has been rejected (e.g., a NAK message), and determines otheravailable alternatives to send the message. Once another network 1102 isidentified from, for example, database 1304 (13), the SU queue manager1208 sends the message to the reverse SCR server 1222 (14) which placesthe message into the protocol that is utilized by the complementarynetwork 1102. The message is then transmitted (15) by, for example, anX.25 line handler 1224 (16) to, for example, a switch 1112 associatedwith the complementary network(s) (shown in FIG. 11). It is preferredthat the complementary network 1102 send an acknowledgement (ACK)message (17, 18) back to the primary network 500 that indicates that themessage has been successfully delivered to the desired complementarynetwork 1102. In the event that the message is not successfullydelivered, the SU queue manager 1208 can repeat the process with thesame or another complementary network that the SU 502, 504, 506 isregistered to.

[0105] In the case of an e-mail message transmitted from a SU in theprimary network to a SU in the secondary network, the host 508 may be,for example, a server associated with the e-mail service. If a SU 502,504, 506 in the primary network substantially covering, for example, theUnited States, sends an e-mail message to a SU 502, 504, 506 in thesecondary network substantially covering, for example, Canada, thesecondary network switch 1112 (or equivalent) will recognize that thereceiving SU 502, 504, 506 is registered in Canada. The secondarynetwork switch 1112 can then transmit the message to the intended SU502, 504, 506 via the normal secondary network transmission process.

[0106] SUs 502, 504, 506 can also use the complementary network 1102 totransmit message traffic to the primary network 500. In this case, thehost 508′ receives, for example, an e-mail message from a SU 502, 504,506 in the secondary network 1102. The host 508′ may also optionally beconnected to another network such as the internet. Once the host 508′receives the e-mail, the host 508′, preferably having substantially thesame functionality as the ACE 514 as described herein, routes themessage to the intended SU 502, 504, 506 in the primary network 500 viathe host computer 108 and ACE as previously discussed.

[0107] Another embodiment of the present invention contemplates the useof a bridge connection between the primary 500 and secondary 1102networks, so that the interface that connects the respective primarynetwork 500 and secondary network 1102 to the bridge have the sameaddress.

[0108]FIG. 14 shows an overview of the inputs to, and outputs from, thereverse SCR server 1222 according to the present invention. As shown,line handler 1224 provides as input a message to the reverse SCR server1222. The characterSCR indicates the character SCR protocol is beingused. However, any other suitable communication protocols) can be usedand practiced with the principles according to the present invention.The operational control server 1402 allows a system operatoradministrator to, for example, issue an audit su command which obtainsthe status of the network and messages being transmitted thereon (e.g.,how many messages are currently flowing over the network, types ofmessages, NAKs, ACKS, etc). The queue manager 1208 can provide an apmmessage to recipient message, which indicates a device-to-device (e.g.,SU to SU) type message. The message from host indicates that any typemessage has been received from a customer host 508. The host status canbe used to indicate, for example, the status of the modem of a hostcomputer 508.

[0109] The response server 1226 handles all of the ACK and NAK messagesbetween the network 500 and any complementary network(s) 1102 and/or1106, as indicated by the outbound message response and outbound statusresponse. The queue manager receives an indication from the reverse SCRserver 1222 when messages have been transmitted (message out) and when amessage has been successfully delivered (delivered msg). Finally, theoperational control server 1402 receives a message (audit su completion)from the reverse SCR server 1402 when the audit process referred toabove has been completed.

[0110] Advantageously, in accordance with one embodiment of the presentinvention, the reverse SCR server 1222 can optionally convert thereceived data from a variety of data transmission protocols, and canoptionally convert or obtain the correct data from a variety of dataformats. For example, as illustrated in FIGS. 15a and 15 b, while thesame data is transmitted, a different data ordering can be used. Thus,the reverse SCR server 1222 is equipped with different dataformat/communication protocols to accept the data in an appropriatemanner. Alternatively, or in addition thereto, the reverse SCR server1222 includes the capability of receiving, converting and/ortransmitting different data protocols.

[0111] More particularly, as shown in FIG. 15a, a first message protocolis shown 1500. The header and routing field 1504 may be followed by asending unit ID field 1508 and a receiving unit ID field 1510. Finally,the protocol may have one or more data fields 1512, which are followedby an end of packet field 1514. In FIG. 15b, the second protocol maycomprise 1516 a header field 1518, followed by a routing field 1520, asending unit ID field 1522, a receiving unit ID field, one or more datafields, and an end of packet field. The reverse SCR server 1222 may useone or more protocol conversions to interpret and transmit the messageusing the different data format in FIGS. 15a and 15 b from one networkto another (e.g., network 500 to network 1102 and/or 1106). Reverse SCRserver 1222 may optionally utilize the message header as the means orthe method in determining the different data protocols to be utilized.

[0112]FIGS. 16a and 16 b, taken together, is a flowchart of the processfor transmitting data to a device that can communicate between two ormore networks in accordance with the present invention. In step 1602,SUs are registered with the networks (e.g., primary network 500 and/orsecondary network 1102 and/or satellite network 1106) in which they maycommunicate. The registration or communication is preferably done inaccordance standard registration processes for each respective network.Such registration information may be stored in the SU informationdatabase 1308, as previously discussed.

[0113] A message is then received in the primary network 1604 (e.g.,network 500), after which time internal transmission and/or routingheaders for the primary network are added to the message 1606, and theintended SU 502, 504, 506 that is to receive the message is registeredto at least the primary network 500 and any secondary network(s) (e.g.,secondary network 1102) 1608.

[0114] If it is determined that the device is not registered 1610, adevice not registered message (or equivalent) is transmitted back to theoriginating SU 502, 504, 506 via the originating network. If it isdetermined that the device is registered, 1610, the message is queuedfor delivery 1612, and subsequently delivered to the primary networkthat is currently processing the message. If the message has beensuccessfully delivered to the intended SU(s) 502, 504, 506 in theprimary network, an ACK message is preferably send to the sending SU. Ifthe message has not been successfully delivered, then the message isqueued for delivery to one or more secondary networks with which thereceiving SU 502, 504, 506 is registered 1620. Any transmission and/orrouting headers for the primary network are removed, and appropriateheaders for transmission to a secondary network are added 1622. Themessage is then delivered to a designated secondary network 1624,preferably in accordance with the information provided in a databasesuch as SUINFO database 1308. Steps 1620, 1622 and 1624 can be repeatedfor each secondary network to which the intended receiving SU isregistered. In addition, steps 1620, 1622 and 1624 can be repeated insequence for each network, or in parallel for each network.

[0115] If the message delivery is successful 1626, an ACK message can besent to the secondary network, primary network and/or sending SU 502,504, 506 that the message has been delivered. If after an attempt hasbeen made to deliver the message to all secondary networks to which thereceiving SU 502, 504, 506 is registered, a NAK message can be sent tothe sending SU 502, 504, 506 that the message was not delivered.

[0116] The many features and advantages of the invention are apparentfrom the detailed specification, and thus, it is intended by theappended claims to cover all such features and advantages of theinvention which fall within the true spirit and scope of the invention.Further, since numerous modifications and variations will readily occurto those skilled in the art, it is not desired to limit the invention tothe exact construction and operation illustrated and described, andaccordingly, all suitable modifications and equivalents may be resortedto, falling within the scope of the invention. While the foregoinginvention has been described in detail by way of illustration andexample of preferred embodiments, numerous modifications, substitutions,and alterations are possible without departing from the scope of theinvention defined in the following claims.

Having thus described our invention, what we claim as new and desire tosecure by Letters Patent is as follows:
 1. A system enabling a firstdevice operatively communicable with at least a first wireless networkto transmit a data message to at least one wireless device operativelycommunicable with said first wireless network and at least a secondwireless network, said system comprising: a host computer, operativelycommunicable with said first wireless network, capable of receiving adata message from the first device; said first wireless networkcomprising a routing switch that: receives the data message from saidhost computer; reads a profile of the at least one wireless device, theprofile comprising data pertaining to at least a primary network and asecondary network to which the at least one wireless device isregistered with, wherein the primary network and secondary network aresaid first wireless network and said second wireless network,respectively; adds a radio frequency header to the message; transmitsthe message to said at least one wireless device in the primary networkand, after a predetermined number of transmission attempts, receives anegative acknowledgement message from the primary network; adds amessage transmission header in accordance with the protocol used by thesecondary network; and transmits the message to the secondary network;and a switch operatively communicable with the secondary network forreceiving the message transmitted by said routing switch andtransmitting the message to at least one of said at least one wirelessdevice via the secondary network.
 2. The system according to claim 1,wherein said routing switch queues each message prior to transmitting tosaid at least one second wireless network.
 3. The system according toclaim 1 wherein said switch receives a negative acknowledgement messagefrom the secondary network.
 4. The system according to claim 1 whereinthe first device is a wireless device registered with at least saidfirst wireless network.
 5. The system according to claim 1 wherein thefirst device is a non-wireless device registered with at least saidfirst wireless network.
 6. A system enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: a first wireless network comprising a routing switchthat: receives the data message from the first device; reads a profileof the at least one wireless device, the profile comprising datapertaining to at least a primary network and a secondary network towhich the at least one wireless device is registered with, wherein theprimary network and secondary network are said first wireless networkand said second wireless network, respectively; adds a radio frequencyheader to the message; transmits the message to said at least onewireless device in the primary network and, after a predetermined numberof transmission attempts, receives a negative acknowledgement messagefrom the primary network; adds a message transmission header inaccordance with the protocol used by the secondary network; andtransmits the message to the secondary network; and a switch operativelycommunicable with the secondary network for receiving the messagetransmitted by said routing switch and transmitting the message to atleast one of said at least one wireless device via the secondarynetwork.
 7. The system according to claim 6, wherein said routing switchqueues each message prior to transmitting to said at least one secondwireless network.
 8. The system according to claim 6 wherein said switchreceives a negative acknowledgement message from the secondary network.9. The system according to claim 6 wherein the first device is awireless device registered with at least said first wireless network.10. The system according to claim 6 wherein the first device is anon-wireless device registered with at least said first wirelessnetwork.
 11. A system for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: a host computer, operatively communicable with saidfirst wireless network, capable of receiving a data message from thefirst device; said first wireless network comprising a routing switchcomprising: an internal routing server that receives the message fromsaid host computer and attaches to the message transmission headers forinternal routing within said first wireless network; a request serverfor reading a profile of the at least one wireless device, the profilecomprising data pertaining to at least a primary network and a secondarynetwork to which the at least one wireless device is registered with,wherein the primary network and secondary network are said firstwireless network and said second wireless network, respectively; arouting server operatively communicable with said request server foradding a radio frequency header to the message, transmitting the messageto at least one of said at least one wireless device in the primarynetwork and, after a predetermined number of transmission attempts,optionally receiving a negative acknowledgement message from the primarynetwork and transmitting the negative acknowledgement message to saidrouting server; a complementary network server for receiving the messagefrom said routing server and adding a message transmission header inaccordance with the protocol used by the secondary network; and a switchoperatively communicable with the secondary network for receiving themessage transmitted by said complementary network server andtransmitting the message to said at least one wireless device via thesecondary network.
 12. The system according to claim 11, wherein saidrouting switch further comprises a message queue operativelycommunicable with at least one of said request server, said routingserver, and said complementary network server that manages the flow ofeach message from said at least one first wireless network to said atleast one second wireless network.
 13. The system according to claim 11wherein said switch comprises: a second routing server for adding aradio frequency header to the message and transmitting the message tothe secondary network and, after a predetermined number of transmissionattempts, optionally receiving a negative acknowledgement message fromthe secondary network.
 14. The system according to claim 11 wherein thefirst device is a wireless device registered with at least said firstwireless network.
 15. The system according to claim 11 wherein the firstdevice is a non-wireless device registered with at least said firstwireless network.
 16. A system for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: a first wireless network comprising a routing switchcomprising: an internal routing server that receives the message andattaches to the message transmission headers for internal routing withinsaid first wireless network; a request server for reading a profile ofthe at least one wireless device, the profile comprising data pertainingto at least a primary network and a secondary network to which the atleast one wireless device is registered with, wherein the primarynetwork and secondary network are said first wireless network and saidsecond wireless network, respectively; a routing server operativelycommunicable with said request server for adding a radio frequencyheader to the message, transmitting the message to at least one of saidat least one wireless device in the primary network and, after apredetermined number of transmission attempts, optionally receiving anegative acknowledgement message from the primary network andtransmitting the negative acknowledgement message to said routingserver; a complementary network server for receiving the message fromsaid routing server and adding a message transmission header inaccordance with the protocol used by the secondary network; and a switchoperatively communicable with the secondary network for receiving themessage transmitted by said complementary network server andtransmitting the message to said at least one wireless device via thesecondary network.
 17. The system according to claim 16, wherein saidrouting switch further comprises a message queue operativelycommunicable with at least one of said request server, said routingserver, and said complementary network server that manages the flow ofeach message from said at least one first wireless network to said atleast one second wireless network.
 18. The system according to claim 16wherein said switch comprises: a second routing server for adding aradio frequency header to the message and transmitting the message tothe secondary network and, after a predetermined number of transmissionattempts, optionally receiving a negative acknowledgement message fromthe secondary network.
 19. The system according to claim 16 wherein thefirst device is a wireless device registered with at least said firstwireless network.
 20. The system according to claim 16 wherein the firstdevice is a non-wireless device registered with at least said firstwireless network.
 21. A system for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: a host computer, operatively communicable with saidfirst wireless network, capable of receiving a data message from thefirst device; said first wireless network comprising a routing switchcomprising: at least a first line handler for receiving the data messagefrom said host computer; a request server for reading a profile of theat least one wireless device, the profile comprising data pertaining toat least a primary network and a secondary network to which the at leastone wireless device is registered with, wherein the primary network andsecondary network are said first wireless network and said secondwireless network, respectively; a routing server operativelycommunicable with said request server for adding a radio frequencyheader to the message; at least a second line handler for receiving themessage from said routing server and transmitting the message to atleast one of said at least one wireless device in the primary networkand, after a predetermined number of transmission attempts, receiving anegative acknowledgement message from the primary network andtransmitting the negative acknowledgement message to said routingserver; a complementary network server for receiving the message fromsaid routing server and adding a message transmission header inaccordance with the protocol used by the secondary network; and at leasta third line handler for receiving the message from said complementarynetwork server and transmitting the message to the secondary network;and a switch operatively communicable with the secondary network forreceiving the message transmitted by said third line handler andtransmitting the message to at least one of said at least one wirelessdevice via the secondary network.
 22. The system according to claim 21,wherein said routing switch further comprises a message queueoperatively communicable with at least one of said request server, saidrouting server, and said complementary network server that manages theflow of each message from said at least one first wireless network tosaid at least one second wireless network.
 23. The system according toclaim 21 wherein said switch comprises: a second routing server foradding a radio frequency header to the message; and at least a fourthline handler for receiving the message from said second routing serverand transmitting the message to the secondary network and, after apredetermined number of transmission attempts, optionally receiving anegative acknowledgement message from the secondary network.
 24. Thesystem according to claim 21 wherein the first device is a wirelessdevice registered with at least said first wireless network.
 25. Thesystem according to claim 21 wherein the first device is a non-wirelessdevice registered with at least said first wireless network.
 26. Asystem for enabling a first device operatively communicable with atleast a first wireless network to transmit a data message to at leastone wireless device operatively communicable with said first wirelessnetwork and at least a second wireless network, said system comprising:a first wireless network comprising a routing switch comprising: atleast a first line handler for receiving the data message; a requestserver for reading a profile of the at least one wireless device, theprofile comprising data pertaining to at least a primary network and asecondary network to which the at least one wireless device isregistered with, wherein the primary network and secondary network aresaid first wireless network and said second wireless network,respectively; a routing server operatively communicable with saidrequest server for adding a radio frequency header to the message; atleast a second line handler for receiving the message from said routingserver and transmitting the message to at least one of said at least onewireless device in the primary network and, after a predetermined numberof transmission attempts, receiving a negative acknowledgement messagefrom the primary network and transmitting the negative acknowledgementmessage to said routing server; a complementary network server forreceiving the message from said routing server and adding a messagetransmission header in accordance with the protocol used by thesecondary network; and at least a third line handler for receiving themessage from said complementary network server and transmitting themessage to the secondary network; and a switch operatively communicablewith the secondary network for receiving the message transmitted by saidthird line handler and transmitting the message to at least one of saidat least one wireless device via the secondary network.
 27. The systemaccording to claim 26, wherein said routing switch further comprises amessage queue operatively communicable with at least one of said requestserver, said routing server, and said complementary network server thatmanages the flow of each message from said at least one first wirelessnetwork to said at least one second wireless network.
 28. The systemaccording to claim 26 wherein said switch comprises: a second routingserver for adding a radio frequency header to the message; and at leasta fourth line handler for receiving the message from said second routingserver and transmitting the message to the secondary network and, aftera predetermined number of transmission attempts, optionally receiving anegative acknowledgement message from the secondary network.
 29. Thesystem according to claim 26 wherein the first device is a wirelessdevice registered with at least said first wireless network.
 30. Thesystem according to claim 26 wherein the first device is a non-wirelessdevice registered with at least said first wireless network.
 31. Asystem enabling a first device operatively communicable with at least afirst wireless network to transmit a data message to at least onewireless device operatively communicable with said first wirelessnetwork and at least a second wireless network, said system comprising:a first wireless network comprising a routing switch that: a) receivesthe data message; b) reads a profile of the at least one wirelessdevice, the profile comprising data pertaining to at least a primarynetwork and a secondary network to which the at least one wirelessdevice is registered with, wherein the primary network and secondarynetwork are said first wireless network and said second wirelessnetwork, respectively; c) determines at least one of the primary andsecondary network at which the last message was received by the at leastone wireless device; d) adds a radio frequency header to the message inaccordance with the network as determined in c); e) transmits themessage to said at least one wireless device in the network asdetermined in c) and, after a predetermined number of transmissionattempts, receives a negative acknowledgement message; f) adds a messagetransmission header in accordance with the protocol used by at least oneof the primary and secondary network to which the message has not yetbeen transmitted; and g) transmits the message to the at least onewireless device in network as determined in f); and a switch operativelycommunicable with the secondary network for receiving the messagetransmitted by said routing switch at at least one of e) and g).
 32. Amethod for enabling a first device operatively communicable with atleast a first wireless network to transmit a data message to at leastone wireless device operatively communicable with the first wirelessnetwork and at least a second wireless network, said method comprisingthe steps of: transmitting a message from the first device to at leastthe first wireless network; reading a profile of the at least onewireless device, the profile comprising data pertaining to at least aprimary network and a secondary network to which the at least onewireless device is registered with, wherein the primary network andsecondary network are said first wireless network and said secondwireless network, respectively; adding a radio frequency header to themessage; transmitting the message to at least one of said at least onewireless device in the primary network and, after a predetermined numberof transmission attempts, optionally receiving a negativeacknowledgement message from the primary network; adding a messagetransmission header in accordance with the protocol used by thesecondary network; transmitting the message to the secondary network;and receiving the message at the secondary network and furthertransmitting the message to at least one of said at least one wirelessdevice via the secondary network.
 33. The method according to claim 32,further comprising the step of queuing each message prior totransmitting to the at least one second wireless network.
 34. The methodaccording to claim 32 wherein the secondary network generates a negativeacknowledgement message subsequent to determining that the messagecannot be delivered.
 35. The method according to claim 32 wherein thefirst device is a wireless device registered with at least the firstwireless network.
 36. The method according to claim 32 wherein the firstdevice is a non-wireless device registered with at least the firstwireless network.
 37. A method for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withthe first wireless network and at least a second wireless network, saidmethod comprising the steps of: a) transmitting a message from the firstdevice to at least the first wireless network; b) reading a profile ofthe at least one wireless device, the profile comprising data pertainingto at least a primary network and a secondary network to which the atleast one wireless device is registered with, wherein the primarynetwork and secondary network are said first wireless network and saidsecond wireless network, respectively; c) determining at least one ofthe primary and secondary network at which the last message was receivedby the at least one wireless device; d) adding a radio frequency headerto the message in accordance with the network as determined in said stepc); e) transmitting the message to said at least one wireless device inthe network as determined in said step c) and, after a predeterminednumber of transmission attempts, receiving a negative acknowledgementmessage; f) adding a message transmission header in accordance with theprotocol used by at least one of the primary and secondary network towhich the message has not yet been transmitted; and g) transmitting themessage to the at least one wireless device in network as determined insaid step f).
 38. A method for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withthe first wireless network and at least a second wireless network, saidmethod comprising: transmitting a message from the first wireless deviceto at least the first wireless network; attaching to the messagetransmission headers for internal routing within the first wirelessnetwork; reading a profile of the at least one wireless device, theprofile comprising data pertaining to at least a primary network and asecondary network to which the at least one wireless device isregistered with, wherein the primary network and secondary network aresaid first wireless network and said second wireless network,respectively; adding a radio frequency header to the message;transmitting the message to at least one of the at least one wirelessdevice in the primary network and, after a predetermined number oftransmission attempts, optionally receiving a negative acknowledgementmessage from the primary network; adding a message transmission headerin accordance with the protocol used by the secondary network; andtransmitting the message to the at least one wireless device via thesecondary network.
 39. The method according to claim 38, furthercomprising the step of queuing messages prior to transmitting from theat least one first wireless network to the at least one second wirelessnetwork.
 40. The method according to claim 38 further comprising thestep of adding a radio frequency header to the message the secondarynetwork and, after a predetermined number of transmission attempts,optionally receiving a negative acknowledgement message from thesecondary network.
 41. The method according to claim 38 wherein thefirst device is a wireless device registered with at least the firstwireless network.
 42. The method according to claim 38 wherein the firstdevice is a non-wireless device registered with at least the firstwireless network.
 43. A method for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withthe first wireless network and at least a second wireless network, saidmethod comprising the steps of: transmitting a message from the firstwireless device to a a host computer operatively communicable with saidfirst wireless network; providing at least a first line handler forreceiving the data message from the host computer; reading a profile ofthe at least one wireless device, the profile comprising data pertainingto at least a primary network and a secondary network to which the atleast one wireless device is registered with, wherein the primarynetwork and secondary network are said first wireless network and saidsecond wireless network, respectively; adding a radio frequency headerto the message; transmitting the message to at least one of said atleast one wireless device in the primary network and, after apredetermined number of transmission attempts, receiving a negativeacknowledgement message from the primary network; adding a messagetransmission header in accordance with the protocol used by thesecondary network; transmitting the message to the secondary network;and transmitting the message to at least one of said at least onewireless device via the secondary network.
 44. The method according toclaim 43, further comprising the step of queuing the message prior totransmission from the at least one first wireless network to the atleast one second wireless network.
 45. The method according to claim 43further comprising the steps of: adding at the secondary network a radiofrequency header to the message; and transmitting the message to thesecondary network and, after a predetermined number of transmissionattempts, optionally receiving a negative acknowledgement message fromthe secondary network.
 46. The method according to claim 43 wherein thefirst device is a wireless device registered with at least the firstwireless network.
 47. The method according to claim 43 wherein the firstdevice is a non-wireless device registered with at least the firstwireless network.
 48. A communication system enabling communicationdevices to communicate across complimentary networks, comprising: afirst communication device transmitting a data message and communicatingsubstantially consistent with a first communication format; a firstwireless network operatively connected to, and directly communicatingwith, said first communication device and receiving the data message,said first wireless network determining responsive to the data messagewhether the data message is to be transmitted within said first wirelessnetwork, and when the data message is to be transmitted within saidfirst wireless network, formatting the data message to be receivedsubstantially consistent with the first communication format, routingthe data message to a device destination within said first wirelessnetwork, and optionally via first wireless communication, and when thedata message is not to be transmitted within said first wirelessnetwork, said first wireless network formatting the data message inaccordance with a second communication format and routing the datamessage to a network destination, optionally via the first wirelesscommunication; a second communication device not capable of directlycommunicating with said first wireless network and communicating inaccordance with the second communication format; a second wirelessnetwork operatively connected to, and directly communicating with, saidsecond communication device and said first wireless network, said secondwireless network receiving the data message from the first wirelessnetwork as the network destination when the data message is not to betransmitted within said first wireless network, optionally via secondwireless communication and routing the data message to said secondcommunication device as the device destination responsive to said secondcommunication format formatted by said first wireless network.
 49. Thesystem according to claim 48 wherein the first communication device is awireless device registered with at least said first wireless network.50. The system according to claim 48 wherein the first communicationdevice is a non-wireless device registered with at least said firstwireless network.
 51. A communication system enabling communicationdevices to communicate across complimentary networks, comprising: afirst communication device transmitting a data message and communicatingsubstantially consistent with a first communication format; a firstwireless network operatively connected to, and directly communicatingwith, said first communication device and receiving the data message,said first wireless network determining responsive to the data messagewhether the data message is to be transmitted within said first wirelessnetwork, and when the data message is to be transmitted within saidfirst wireless network, formatting the data message to be receivedsubstantially consistent with the first communication format,transmitting the data message to a device destination within said firstwireless network, and optionally via first wireless communication, andwhen the data message is not to be transmitted within said firstwireless network, said first wireless network formatting the datamessage in accordance with a second communication format andtransmitting the data message to a network destination, optionally viathe first wireless communication; a second communication device notcapable of directly communicating with said first wireless network andcommunicating in accordance with the second communication format; asecond wireless network operatively connected to, and directlycommunicating with, said second communication device and said firstwireless network, said second wireless network receiving the datamessage from the first wireless network as the network destination whenthe data message is not to be transmitted within said first wirelessnetwork, optionally via second wireless communication and transmittingthe data message to said second communication device as the devicedestination responsive to said second communication format formatted bysaid first wireless network.
 52. The system according to claim 51wherein the first communication device is a wireless device registeredwith at least said first wireless network.
 53. The system according toclaim 51 wherein the first communication device is a non-wireless deviceregistered with at least said first wireless network.
 54. Acommunication system enabling communication devices to communicateacross complimentary networks, comprising: a first communication devicetransmitting a data message and communicating in accordance with a firstcommunication format; a primary wireless network operatively connectedto, and directly communicating with, said first communication device andreceiving the data message, said primary wireless network determiningresponsive to the data message whether the data message is to bebroadcast within said primary wireless network and outside said primarywireless network, and when the data message is to be broadcast withinsaid primary wireless network, formatting the data message to bereceived in accordance with the first communication format, routing thedata message to a device destination within said primary wirelessnetwork via first wireless communication, and when the data message isto be transmitted outside said primary wireless network, optionally inaddition to the routing the data message within said primary wirelessnetwork, said primary wireless network formatting the data message inaccordance with a second communication format and routing the datamessage outside said primary network; a second communication device notcapable of directly communicating with said primary wireless network andcommunicating in accordance with the second communication format; acomplimentary wireless network operatively connected to, and directlycommunicating with, said second communication device and said primarilywireless network, said complimentary wireless network receiving the datamessage from the primary wireless network and routing the data messageto said second communication device responsive to said secondcommunication format formatted by said primary wireless network.
 55. Thesystem according to claim 54 wherein the first communication device is awireless device registered with at least said first wireless network.56. The system according to claim 54 wherein the first communicationdevice is a non-wireless device registered with at least said firstwireless network.
 57. A communication system enabling communicationdevices to communicate across complimentary networks, comprising; afirst communication device transmitting a data message and communicatingin accordance with a first communication format; a primary wirelessnetwork operatively connected to, and directly communicating with, saidfirst communication device and receiving the data message, said primarywireless network determining responsive to the data message whether thedata message is to be broadcast within said primary wireless network andoutside said primary wireless network, and when the data message is tobe broadcast within said primary wireless network, formatting the datamessage to be received in accordance with the first communicationformat, transmitting the data message to a device destination withinsaid primary wireless network via first wireless communication, and whenthe data message is to be transmitted outside said primary wirelessnetwork, optionally in addition to the transmitting the data messagewithin said primary wireless network, said primary wireless networkformatting the data message in accordance with a second communicationformat and transmitting the data message outside said primary network; asecond communication device not capable of directly communicating withsaid primary wireless network and communicating in accordance with thesecond communication format; a complimentary wireless networkoperatively connected to, and directly communicating with, said secondcommunication device and said primarily wireless network, saidcomplimentary wireless network receiving the data message from theprimary wireless network and transmitting the data message to saidsecond communication device responsive to said second communicationformat formatted by said primary wireless network.
 58. The systemaccording to claim 57 wherein the first communication device is awireless device registered with at least said first wireless network.59. The system according to claim 57 wherein the first communicationdevice is a non-wireless device registered with at least said firstwireless network.
 60. A system enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: means for processing, operatively communicable withsaid first wireless network, capable of receiving a data message fromthe first device; said first wireless network comprising switching meansthat: receives the data message from said means for processing; reads aprofile of the at least one wireless device, the profile comprising datapertaining to at least a primary network and a secondary network towhich the at least one wireless device is registered with, wherein theprimary network and secondary network are said first wireless networkand said second wireless network, respectively; adds a radio frequencyheader to the message; transmits the message to said at least onewireless device in the primary network and, after a predetermined numberof transmission attempts, receives a negative acknowledgement messagefrom the primary network; adds a message transmission header inaccordance with the protocol used by the secondary network; andtransmits the message to the secondary network; and a switch operativelycommunicable with the secondary network for receiving the messagetransmitted by said switching means and transmitting the message to atleast one of said at least one wireless device via the secondarynetwork.
 61. A system for enabling a first device operativelycommunicable with at least a first wireless network to transmit a datamessage to at least one wireless device operatively communicable withsaid first wireless network and at least a second wireless network, saidsystem comprising: means for processing, operatively communicable withsaid first wireless network, capable of receiving a data message fromthe first device; said first wireless network comprising a routingswitch comprising: an internal routing server that receives the messagefrom said means for processing and attaches to the message transmissionheaders for internal routing within said first wireless network; arequest server for reading a profile of the at least one wirelessdevice, the profile comprising data pertaining to at least a primarynetwork and a secondary network to which the at least one wirelessdevice is registered with, wherein the primary network and secondarynetwork are said first wireless network and said second wirelessnetwork, respectively; a routing server operatively communicable withsaid request server for adding a radio frequency header to the message,transmitting the message to at least one of said at least one wirelessdevice in the primary network and, after a predetermined number oftransmission attempts, optionally receiving a negative acknowledgementmessage from the primary network and transmitting the negativeacknowledgement message to said routing server; a complementary networkserver for receiving the message from said routing server and adding amessage transmission header in accordance with the protocol used by thesecondary network; and means for switching, operatively communicablewith the secondary network, that receives the message transmitted bysaid complementary network server and transmits the message to said atleast one wireless device via the secondary network.
 62. In a datacommunication system having a first device operatively communicable withat least a first wireless network to transmit a data message to at leastone wireless device operatively communicable with the first wirelessnetwork and at least a second wireless network, wherein the system hasmeans for processing, operatively communicable with said first wirelessnetwork, capable of receiving a data message from the first device, andwherein the first wireless network has: a routing switch having aninternal routing server that receives the message from the means forprocessing and attaches to the message transmission headers for internalrouting within the first wireless network, a request server for readinga profile of the at least one wireless device, the profile comprisingdata pertaining to at least a primary network and a secondary network towhich the at least one wireless device is registered with, wherein theprimary network and secondary network are the first wireless network andthe second wireless network, respectively, a routing server operativelycommunicable with the request server for adding a radio frequency headerto the message, transmitting the message to at least one of the at leastone wireless device in the primary network and, after a predeterminednumber of transmission attempts, optionally receiving a negativeacknowledgement message from the primary network and transmitting thenegative acknowledgement message to said routing server, and acomplementary network server for receiving the message from said routingserver and adding a message transmission header in accordance with theprotocol used by the secondary network, and wherein the secondarynetwork has means for switching, operatively communicable with thesecondary network, that receives the message transmitted by thecomplementary network server and transmits the message to the at leastone wireless device via the secondary network, a method of enabling thefirst device to transmit a data message to the at least one wirelessdevice, said method comprising the steps of: transmitting a message fromthe first device to at least the first wireless network; reading aprofile of the at least one wireless device, the profile comprising datapertaining to at least a primary network and a secondary network towhich the at least one wireless device is registered with, wherein theprimary network and secondary network are said first wireless networkand said second wireless network, respectively; adding a radio frequencyheader to the message; transmitting the message to at least one of saidat least one wireless device in the primary network and, after apredetermined number of transmission attempts, optionally receiving anegative acknowledgement message from the primary network; adding amessage transmission header in accordance with the protocol used by thesecondary network; transmitting the message to the secondary network;and receiving the message at the secondary network and furthertransmitting the message to at least one of said at least one wirelessdevice via the secondary network.
 63. In a data communication systemhaving a routing switch with an internal routing server that receivesthe message from means for processing and attaches to the messagetransmission headers for internal routing within a wireless network, arequest server for reading a profile of the at least one wirelessdevice, the profile comprising data pertaining to at least a firstnetwork and a second network to which the at least one wireless deviceis registered with, a routing server operatively communicable with therequest server for adding a radio frequency header to the message,transmitting the message to at least one of the at least one wirelessdevice in the first network and, after a predetermined number oftransmission attempts, optionally receiving a negative acknowledgementmessage from the first network and transmitting the negativeacknowledgement message to said routing server, and a complementarynetwork server for receiving the message from said routing server andadding a message transmission header in accordance with the protocolused by the second network, and wherein the second network has means forswitching, operatively communicable with the secondary network, thatreceives the message transmitted by the complementary network server andtransmits the message to the at least one wireless device via the secondnetwork, a communication system comprising: a first communication devicetransmitting a data message and communicating in accordance with a firstcommunication format; a primary wireless network operatively connectedto, and directly communicating with, said first communication device andreceiving the data message, said primary wireless network determiningresponsive to the data message whether the data message is to bebroadcast within said primary wireless network and outside said primarywireless network, and when the data message is to be broadcast withinsaid primary wireless network, formatting the data message to bereceived in accordance with the first communication format, transmittingthe data message to a device destination within said primary wirelessnetwork via first wireless communication, and when the data message isto be transmitted outside said primary wireless network, optionally inaddition to the transmitting the data message within said primarywireless network, said primary wireless network formatting the datamessage in accordance with a second communication format andtransmitting the data message outside said primary network; a secondcommunication device not capable of directly communicating with saidprimary wireless network and communicating in accordance with the secondcommunication format; a complimentary wireless network operativelyconnected to, and directly communicating with, said second communicationdevice and said primarily wireless network, said complimentary wirelessnetwork receiving the data message from the primary wireless network andtransmitting the data message to said second communication deviceresponsive to said second communication format formatted by said primarywireless network.